Tree preservation zone

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

16 Individual Trees 4 Groups 5 Areas

reference: 1/77/04-436
name: 16 Individual Trees 4 Groups 5 Areas
tree-preservation-order: undefined
1/77/04-436
tree-preservation-zone-type: woodland
geometry: MULTIPOLYGON (((0.188111 51.895773,0.188139 51.895778,0.188151 51.895784,0.188160 51.895791,0.188163 51.895795,0.188168 51.895809,0.188164 51.895822,0.188161 51.895826,0.188148 51.895837,0.188136 51.895842,0.188122 51.895845,0.188107 51.895846,0.188086 51.895843,0.188073 51.895838,0.188063 51.895832,0.188053 51.895820,0.188051 51.895811,0.188052 51.895802,0.188057 51.895793,0.188071 51.895782,0.188083 51.895777,0.188111 51.895773)))
point: POINT (0.188109 51.89581)
notes
entry-date: 1977-03-31
start-date: 1977-03-31
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Uttlesford District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL